<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML3.2 EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="DOCTEXT">
<TITLE>MPI_T_init_thread</TITLE>
</HEAD>
<BODY BGCOLOR="FFFFFF">
<H1 id="MPI_T_init_thread">MPI_T_init_thread</H1>
Initialize the MPI_T execution environment 
<H2>Synopsis</H2>
<PRE>
</PRE>
<PRE>
int MPI_T_init_thread(int required, int *provided)
</PRE>

<P>
<H2>Input Parameters</H2>
<DL>
<DT><B>required </B> <DD> desired level of thread support (integer)
</DL>
<P>
<H2>Output Parameters</H2>
<DL>
<DT><B>provided </B> <DD> provided level of thread support (integer)
</DL>
<P>
<H2>Notes</H2>
<H2>The valid values for the level of thread support are</H2>
<DL>
<DT><B>MPI_THREAD_SINGLE </B> <DD> Only one thread will execute.

<DT><B>MPI_THREAD_FUNNELED </B> <DD> The process may be multi-threaded, but only the main
thread will make MPI_T calls (all MPI_T calls are funneled to the
main thread).

<DT><B>MPI_THREAD_SERIALIZED </B> <DD> The process may be multi-threaded, and multiple
threads may make MPI_T calls, but only one at a time: MPI_T calls are not
made concurrently from two distinct threads (all MPI_T calls are serialized).

<DT><B>MPI_THREAD_MULTIPLE </B> <DD> Multiple threads may call MPI_T, with no restrictions.
</DL>
<P>
<H2>Thread and Interrupt Safety</H2>
<P>
This routine is thread-safe.  This means that this routine may be
safely used by multiple threads without the need for any user-provided
thread locks.  However, the routine is not interrupt safe.  Typically,
this is due to the use of memory allocation routines such as <tt>malloc
</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
<P>
<H2>Errors</H2>
<P>
All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
C routines as the value of the function and Fortran routines in the last
argument.  Before the value is returned, the current MPI error handler is
called.  By default, this error handler aborts the MPI job.  The error handler
may be changed with <tt>MPI_Comm_set_errhandler</tt> (for communicators),
<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
its use is deprecated.  The predefined error handler
<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
Note that MPI does <em>not</em> guarantee that an MPI program can continue past
an error; however, MPI implementations will attempt to continue whenever
possible.
<P>
<DL>
<DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
</DL>
<DL>
<DT><B>MPI_T_ERR_INVALID </B> <DD> Invalid use of the interface or bad parameter values(s).
</DL>
<DL>
<DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
about this error code. 
</DL>
<P>
<H2>See Also</H2>
 MPI_T_finalize
<br>
</BODY></HTML>
